Zen

Translation

English type: Plain text
This is a collection of information on dealing with rpmlint. Note that the first thing you should do is use the `-e` option to rpmlint so that it provides additional explanatory text. For example:
0/1980 · 198

Sign in to save the translation.

English French Actions
Common Rpmlint issues
 
This is a collection of information on dealing with rpmlint. Note that the first thing you should do is use the `-e` option to rpmlint so that it provides additional explanatory text. For example:
 
rpmlint -e description-line-too-long
 
description-line-too-long:
Your description lines must not exceed 80 characters. If a line is exceeding
this number, cut it to fit in two lines.
 
The information provided here is not exhaustive. It covers some scenarios for which quick fixes are known. It is also not a "fix-all" for every scenario and should be carefully considered within the context of building your RPM. Some rpmlint warning should not be fixed for some packages, for example warnings about non-standard groups or users, or about setuid executables may be perfectly right for some packages. You can see descriptions of various rpmlint issues in the files installed by package rpmlint under `/usr/lib/python3.12/site-packages/rpmlint/descriptions/`.
 
For more information on rpmlint project look at link:https://github.com/rpm-software-management/rpmlint[Rpmlint GitHub Project].
 
debuginfo-without-sources
 
`rpmlint -e debuginfo-without-sources` provides a good overall picture. See also xref:packaging-guidelines::index.adoc[Compiler Flags]. To fix, make sure that debugging symbols are created and that they not are stripped so they are available for rpmbuild post-processing.
 
file-not-utf8
 
Indicates that the text encoding of the specified file, usually a documentation file, is not in UTF8.
 
Usually fixed by running `iconv` on the uncompressed file before installation. See man page *ICONV(1)*. For example, to recode a file named AUTHORS encoded in latin-1, you can use:
 
iconv -f iso8859-1 -t utf-8 AUTHORS > AUTHORS.conv && mv -f AUTHORS.conv AUTHORS
 
or check the sample at the link:https://fedoraproject.org/wiki/Perl/Tips#file-not-utf8[Perl] packaging tips page and link:https://fedoraproject.org/wiki/Packaging_tricks#Convert_encoding_to_UTF-8[generic tricks] page.
 
hardcoded-library-path
 
Don't hardcode path in SPEC. Use xref:packaging-guidelines::RPMMacros.adoc[macros] instead.
 
incorrect-fsf-address
 
In all cases, upstream should be informed about this. This is the only requirement with respect to this error.
 

Loading…

User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/CommonRpmlintIssues
  3. French
This is a collection of information on dealing with rpmlint. Note that the first thing you should do is use the `-e` option to rpmlint so that it provides additional explanatory text. For example:
 
3 months ago
Browse all string changes

Glossary

English French
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?"
Source string location
pages/CommonRpmlintIssues.adoc:6
String age
3 months ago
Last updated
3 months ago
Source string age
3 months ago
Translation file
po/fr/master/pages/CommonRpmlintIssues.po, string 2